Let foreground user follow-ups revise paused Goals safely - #186
Closed
ByBrawe wants to merge 18 commits into
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Superseded by the later long-Goal steering architecture shipped through #187 and #189.
The original problem remains important, but this PR's exact user-follow-up-to-contract-revision design is no longer the active architecture: natural-language resume intent moved to the agent/model layer, explicit
/goal editremains the durable contract boundary, and ordinary foreground work is steering rather than implicit contract mutation.Closing this stale branch so it does not compete with the shipped ownership/revision semantics.